home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: MiNT 1.10 re-sync
- Date: Fri, 17 Jun 94 0:21:42 CDT
- From: Juergen Lock <nox@jelal.north.de>
- In-Reply-To: <9406121908.AA10455@irs.inf.tu-dresden.de>; from "Michael Hohmuth" at Jun 12, 94 9:08 pm
- Message-Id: <9406162221.AA00392@jelal.north.de>
-
- Michael Hohmuth writes:
-
- > > 6. and now the sticky text/fragmentation megapatch... does a few things:
- >
- > > . execv..() frees the old process memory before allocating the new ones,
- > > and so no longer leaves holes in your memory map. this took a few
- > > ugly hacks but i think its worth it :) the only visible change should
- > > be when exec'ing a damaged binary the process gets killed, fixing that
- > > would require reading executables twice.
- >
- > Well, that's fine with me, but I don't know whether this "non-posixish"
- > behaviour is tolerable by all others? I guess so... as it effectively
- > makes "damaged executable" equivalent to "executable crashed immediately
- > after it has been run".
-
- or whats on systems that demand-page text instead of loading it all at
- once... do they always check the entire file before?
- >
- > Opinions?
-
- should there be some flag to turn it off? in mint.cnf?
- >
- > Michael
- cheers
- Juergen
- --
- J"urgen Lock / nox@jelal.north.de / UUCP: ..!uunet!unido!uniol!jelal!nox
- ...ohne Gewehr
- PGP public key fingerprint = 8A 18 58 54 03 7B FC 12 1F 8B 63 C7 19 27 CF DA
-